Publishing Security Files
Description
After you have defined security settings, page security, and a login UX component, you need to publish these files to the Application Server.
UPDATE
Guid.SecuritySettings
This is a simple text file that contains a unique identifier to identify the current project folder when validating security for every page request. If it is missing, the server can not identify the project and will block all pages and files.
Project.SecuritySettings
This file contains the main security parameters set in the security settings genie. Even if security is set as off in the genie, this file must be present in the published project folder. If it is missing, the server can not can not determine the security configuration and will block all pages and files.
Pages.SecuritySettings
This is a simple text file that contains the permissions for every page. If security is turned on in the security settings, this file must be present. If the file does not exist, the server will redirect the user to the login denied page. No other page will be available.
SecurityGroups.SecuritySettings
This contains the security group definitions and is not needed for most normal operation. It is only used in the code used for a UX component to show the current user security group assignments. If it is missing and a UX using the code is opened, no security groups will be shown on the UX; if the record is saved, all user permissions will be removed.
SecurityQuestions.SecuritySettings
This text contains a list of security questions that may be used for user validation. It is only used in a UX component to show security questions that may be available for selection. If it is missing and a UX using the code is opened, the UX will not display any questions. as a result, the record cannot be saved.
Limitations
Web publishing applications only.
See Also